Conversation
Co-authored-by: Athan <kgryte@gmail.com>
leofang
left a comment
There was a problem hiding this comment.
LGTM too. One possible nit: IIRC we discussed about raising exceptions for casting to unsupported dtypes by a certain device. Do we want to address it in this PR, or another?
I'd like to have @oleksandr-pavlyk to take a look if possible.
|
@leofang Ah, you're right. We do need to address the condition where the requested device does not support the desired dtype. Although, this applies more generally to all creation functions supporting the |
|
Yup sounds good |
|
Thanks for the PR, LGTM as well. |
|
As this PR has three approvals, will go ahead and merge. We'll submit a follow-up PR to add guidance concerning what should happen when a device does not support an array data type when using |
This PR,
devicekwarg toastypeAPI in the DRAFT versionIt fixes #647 (comment)